-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Campaigns objectives endpoint #12616
Campaigns objectives endpoint #12616
Conversation
📲 You can test the changes from this Pull Request in WooCommerce-Wear Android by scanning the QR code below to install the corresponding build.
|
📲 You can test the changes from this Pull Request in WooCommerce Android by scanning the QR code below to install the corresponding build.
|
b54f306
to
29424db
Compare
…-endpoint # Conflicts: # build.gradle
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## trunk #12616 +/- ##
============================================
- Coverage 40.64% 40.63% -0.01%
Complexity 5673 5673
============================================
Files 1230 1230
Lines 69167 69182 +15
Branches 9579 9580 +1
============================================
Hits 28114 28114
- Misses 38468 38483 +15
Partials 2585 2585 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this @irfano. Changes look good and work as expected. Merging!
Part of: #12469
Description
This adds functions to the
BlazeRepository
for fetching campaign objectives.I haven't included unit tests since the newly added functions don't have complex logic and act as a gateway to the FluxC library.
Warning
do not merge: FluxC reference should be updated to the trunk hash before merging.
Known issue: Although the
campaigns/objectives
endpoint accepts alocale
parameter, the response is not localized on the API side.Steps to reproduce
Fetching objectives is not yet implemented in the UI. The retrieved data can only be viewed using the Database Inspector. To fetch objectives on the Blaze campaign preview screen, apply this patch: Fetch_objectives.patch
Testing information
The data in the Database inspector should be like this:
The tests that have been performed
I verified the stored data in the
BlazeCampaignObjectives
table.RELEASE-NOTES.txt
if necessary. Use the "[Internal]" label for non-user-facing changes.Reviewer (or Author, in the case of optional code reviews):
Please make sure these conditions are met before approving the PR, or request changes if the PR needs improvement: